docs: update lint-staged migration guidance#24
Conversation
|
Warning Review limit reached
Next review available in: 41 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2341e72287
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Do not carry lint-staged CLI flags to `rs staged`; they are not forwarded. Keep standalone lint-staged when the workflow requires function-based configs, CLI options, or behavior outside a plain task map. | ||
| ## CLI Options | ||
|
|
||
| Run `rs staged -h` for supported options. |
There was a problem hiding this comment.
When an existing hook uses a lint-staged-only flag such as --diff for CI/branch diffs, this migration reference now points to help but no longer says to keep standalone lint-staged for unsupported flags. I checked packages/rstack/src/staged.ts: parseArgs is strict: true and the rs staged help only lists --allow-empty, --concurrent, --cwd, --debug, --no-stash, --quiet, --relative, and --verbose, while lint-staged's own help includes additional flags like --diff [string] to override the default git diff --staged behavior and --fail-on-changes; migrating those scripts to rs staged will fail on the unknown option, so this section should explicitly say only the listed options can be carried over.
Useful? React with 👍 / 👎.
1 participant
This PR updates the lint-staged migration reference to reflect function config and CLI option support in
rs staged. It points users tors staged -hfor the current supported option list.